Managing the closed network / AOSP devices

Registration status values

Upon registration to Core, the device sends all device details to Core. The Device Details page > Registration Status field lists the following values:

Table 4.  Registration status values

Action

Registration Status value

Android Enterprise configuration sent to device

Work Managed Device

Closed network / AOSP configuration sent to device

Work Managed Device - Non GMS

Device does not receive the AOSP configuration

The device is retired (factory reset.)

Closed network / AOSP device capabilities

After successful registration, devices will be able to receive and provision the following:

Table 5.  Closed network / AOSP device capabilities

Type

Description

Configurations

  • Android Enterprise

  • Android XML

  • Android APN

  • Exchange

  • MTD

  • Certificates

  • VPN

  • Wi-Fi

Policies

  • Android Quick Setup

  • Android Kiosk

  • Firmware policy

  • Security

  • Privacy

  • Lockdown

  • MTD local actions

  • MTD anti-phishing

  • Compliance policy

  • Sync policy

App Management

  • Support for in-house apps with configurations/restrictions

  • Apps@Work

Standard device management capabilities

All the supported device management commands of Android Enterprise work for closed network / AOSP deployment, except "Shared Kiosk- Signout."

App Management

  • With a closed network / AOSP deployment, devices registered as a non-GMS device will have access to all in-house applications through Apps@Work.

  • In non-closed networks / AOSP deployments, all apps need to be uploaded as in-house apps using their .apks since there is no access to Google's application bundles.

  • When applying app restrictions, make sure to have the Install this app for Android enterprise and Enable AOSP app restrictions check boxes selected.

For more information about app management, see "Adding in-house apps for Android" in the Core Apps@Work Guide.